fix: delete the **bring back** tree node from the undo container remap #423
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When performing undo and redo operations for a tree node deletion, a new
TreeID
is used due to the associated Data MapContainer.However, concurrent operations might bring back the deleted node while keeping its original
TreeID
. This results in the node having two IDs in the undo manager: the original and the newly created one from the redo.To address this, we need to remove the bring-back node from the remapping when importing.